Method and apparatus for communicating securely with a token

ABSTRACT

A method and apparatus to communicate with a token using a previously reserved binary number in the start field of a cycle, wherein the cycle is not echoed on any bus other than the bus through which the communication is received.

BACKGROUND

The Trusted Platform Computing Alliance (TPCA) in the TPCA's Main Specification, Version 1.1a, dated 1 Dec. 2001 describes a Trusted Platform Module (TPM) or token that provides increased confidence and that enables enhancements of existing services and new services. The token supports auditing and logging of software processes, platform boot integrity, file integrity, and software licensing. The token provides a protected information store for the platform (e.g., a personal computer), and can be used to attest to the identity of the platform as defined by the hardware that is present (e.g. processors, chipsets, firmware, etc.) on the platform. The secure features of the token encourage third parties to grant the platform access to information that would otherwise be denied.

The token contains an isolated computing engine whose processes can be trusted because they cannot be altered. These processes and the binding of the subsystem to the platform combine to reliably measure and report the state of the main computing environment inside the platform. The token provides a root of trust for the booting of the platform. A local or remote entity may query the token to reliably obtain security information and decide whether the platform's behavior enables it to be trusted for the intended purpose. Confidence in the loading of software is improved, because the token can attest to the current state of the operating system.

The token may include several registers, that may be used to store encrypted digests of files, including software programs, which may be retrieved and authenticated. Information written to and read from the token is to be secure in order for third parties to trust the platform. The mapping of the registers as traditional Input/Output (I/O) mapped registers is undesirable as a device on the same interface as the token may be programmed to map to the same I/O addresses, thereby compromising the security of the token.

BRIEF DESCRIPTION OF THE DRAWINGS

One or more embodiments of the present invention described herein are illustrated by way of example and not by way of limitation in the accompanying figures. For simplicity and clarity of illustration, elements illustrated in the figures are not necessarily drawn to scale. For example, the dimensions of some elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals have been repeated among the figures to indicate corresponding or analogous elements.

FIG. 1 illustrates a computing device comprising a token according to one embodiment of the invention.

FIG. 2 illustrates a flow diagram for communicating with a token according to one embodiment of the invention.

FIG. 3 illustrates a token write cycle according to one embodiment of the invention.

FIG. 4 illustrates a token read cycle according to one embodiment of the invention.

FIG. 5 illustrates a computing device comprising a chipset with a dual ported register according to one embodiment of the invention.

FIG. 6 illustrates a flow diagram for writing to a token using dual ported registers according to one embodiment of the invention.

FIG. 7 illustrates a flow diagram for reading from a token using dual ported registers according to one embodiment of the invention.

DETAILED DESCRIPTION

Described is a method and apparatus for communicating securely with a token. In the following description, numerous specific details such as communication protocols, types and interrelationships of system components etc. are set forth in order to provide a thorough understanding of the one or more embodiments of the present invention. It will be apparent, however, to one of ordinary skill in the art that the one or more embodiments of the present invention may be practiced without these specific details. In other instances, well-known architectures, control structures, gate level circuits and full software instruction sequences and techniques have not been shown to avoid unnecessarily obscuring this description. Those of ordinary skill in the art, with the included description, will be able to implement appropriate functionality without undue experimentation.

References in the specification to “one embodiment”, “an embodiment”, “an example embodiment”, etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one of ordinary skill in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

In the following description and claims, the terms “coupled” and “connected”, along with derivatives such as “communicatively coupled” may be used. It should be understood that these terms are not intended as synonyms for each other. Rather, in particular embodiments, “connected” may be used to indicate that two or more elements are in direct physical or electrical contact with each other. “Coupled” may mean that two or more elements are in direct physical or electrical contact. However, “coupled” may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other.

Parts of the description are presented using terminology commonly employed by those of ordinary skill in the art to convey the substance of their work to others of ordinary skill in the art. Also, parts of the description will be presented in terms of operations performed through the execution of programming instructions. As well understood by those of ordinary skill in the art, these operations often take the form of electrical, magnetic, or optical signals capable of being stored, transferred, combined, and otherwise manipulated through, for instance, electrical components.

FIG. 1 illustrates a computing device comprising a token according to one embodiment of the invention. An example computing device 100 shown in FIG. 1 may comprise one or more processors 110, a chipset 120, and a token 155.

The processors 110 may support one or more operating modes such as, for example, a real mode, a protected mode, a virtual 8086 mode, and/or a virtual machine mode (VMX mode). Further, the processors 110 may support one or more privilege levels or rings in each of the supported operating modes. In general, the operating modes and privilege levels of a processor 110 define the instructions available for execution and the effect of executing such instructions. More specifically, a processor 110 may be permitted to execute certain privileged instructions only if the processor 110 is in an appropriate mode and/or privilege level. In one embodiment of the invention, a processor 110 may comprise a microcode memory 102 to store trusted microcode.

Processors 110 are coupled to chipset 120 via a processor bus 164. Although FIG. 1 illustrates two processors 110 connected to chipset 120 via a common processor bus 164, alternate embodiments of the invention may have multiple processors 110 with each processor 110 connected to chipset 120 directly by, e.g., a point-to-point processor bus. In one embodiment of the invention, the processor bus 164 is a front side bus (FSB) as used with Intel® corporation's Pentium 4 processor. Chipset 120 may comprise one or more integrated circuit packages or chips.

In one embodiment of the invention chipset 120 includes processor bus interface (I/F) logic 104 coupled between processor bus 164 and decoder logic 103. In one embodiment of the invention, chipset 120 includes memory bus interface logic 106 to couple the chipset 120 to a memory 130 via a memory bus 166. In one embodiment of the invention, memory 130 includes trusted code 131. In one embodiment of the invention, trusted code 131 may be program code and/or data that is authenticated by a processor 110 and stored as trusted code 102 in a processor 110.

In one embodiment of the invention, chipset 120 includes Input/Output (I/O) bus interface logic 112 connected to I/O devices 113 via, e.g., I/O bus 168. A second I/O bus interface logic 107 couples chipset 120 to a network controller 140 using, e.g., I/O bus 169.

In one embodiment of the invention, network controller 140 connects computing device 100 to one or more remote computing devices 119 via a network 122. For example, network controller 140 may comprise a 10 Mb or 100 Mb Ethernet controller, a cable modem, a digital subscriber line (DSL) modem, plain old telephone service (POTS) modem, etc. to couple the computing device 100 to one or more remote computing devices 119.

A third I/O bus interface logic 108 couples chipset 120 to one or more storage devices 114 using, e.g., a I/O bus 171. A graphics bus interface logic 109 couples chipset 120 to a graphics controller 115 via a graphics bus 174. Graphics controller 115 is coupled to display device 116.

I/O bus I/F logic 105 couples chipset 120 to token 155 using an I/O bus 162. In one embodiment of the invention, I/O bus 162 may be a low pin count (LPC) bus. Token 155 comprises one or more registers 156, bus master engine 157, and I/O bus interface logic 158. Also connected to I/O bus 162 is a super I/O controller 118 that is coupled to, e.g., a keyboard, a mouse etc.

FIG. 2 illustrates a flow diagram for communicating with a token according to one embodiment of the invention. As FIG. 2 illustrates, at 210 a processor 110 issues a read or write request to chipset 120. At 215, chipset 120 receives the request from processor 110 via processor bus 164. At 220, chipset 120 decodes the address in the request. In one embodiment of the invention, in addition to decoding the address the chipset 120 decodes the cycle type in the request. At 225, the processor bus I/F logic 104 determines whether the request is a trusted request. In one embodiment of the invention, the processor bus I/F logic 104 determines this by determining whether the decoded address is within the trusted configuration space, and by determining whether a value in a request identity field in the request is a value that indicates the request is a trusted request. If the request is not a trusted request, at 225, the chipset 120 aborts the request. At 230 the processor bus I/F logic 104 determines whether the request targets token 155. If the processor bus I/F logic 104 determines that the request targets token 155 e.g., by determining the offset range is within the specified range, at 235 the processor bus I/F logic 104 forwards the request to the I/O bus I/F logic 105. If the request does not target the token 155, at 255, the chipset 120 aborts the request. At 240, the I/O bus I/F logic 105 forwards the request over I/O bus 162 to I/O bus interface logic 158. In one embodiment of the invention, the I/O bus interface logic 158 uses a token cycle that includes a code that ensures that other devices on the I/O bus ignore the forwarded request. In one embodiment of the invention, the code comprises a reserved binary number that is ignored by other devices on the I/O bus 162. At 245, when forwarding the request using the code the I/O bus I/F logic 105 ensures that information in the request is suppressed on one or more other busses except on the I/O bus 162. In one embodiment of the invention, the information in the request may be suppressed by sending false data on one or more busses other than the I/O bus 162 to suppress information from the request echoed on one or more other busses. In one embodiment of the invention, both the address and the data contained in the echoed code may be distorted e.g., by writing a series of invalid bits in the address and data fields. At 250, the request is completed.

Referring to FIG. 1, in one embodiment of the invention, processor bus interface (I/F) logic 104 comprises buffers and logic circuits to receive a trusted cycle (e.g., a read, or a write cycle) from a processor 110. In one embodiment of the invention, the processor bus I/F logic 104 identifies the trusted cycle by identifying a unique value in a field in the trusted cycle. In addition, the trusted cycle may address a location in a trusted configuration space.

In one embodiment of the invention, a trusted cycle may comprise a standard memory read or write cycle to the configuration space provided that the chipset 120 has been preprogrammed to allow standard memory read or write cycles. In one embodiment of the invention, the preprogramming of the chipset 120 is done using a trusted memory cycle to execute the program that preprograms the chipset 120.

The processor bus I/F logic 104 sends the trusted cycle to decoder logic 103. Decoder logic 103 decodes the trusted cycle and determines whether the address in the trusted cycle is a valid address in token 155. If the address in the trusted cycle is a valid address in token 155, the trusted cycle or the information in the trusted cycle is sent to I/O bus I/F logic 105. However, if the address in the trusted cycle is not a valid address, in one embodiment of the invention, the decoder logic 103 may inform the processor bus I/F logic 104 to abort the trusted cycle. However, if the processor bus I/F logic 104 has already received the entire trusted cycle, the processor bus I/F logic 104 discards the trusted cycle if the decoded address is not a valid address. In other embodiments of the invention the processor bus I/F logic 104 may return some arbitrary data, e.g., a series of 0's or 1's or may reset computing device 100. Other processor cycles may also be received by processor bus interface logic 104 e.g., a non trusted memory cycle or a non trusted I/O.

Processor bus I/F logic 104 may be coupled to other bus interface logic e.g., to memory bus I/F logic 106. So also the other bus I/F logic may be connected to each other via busses in order to communicate with each other and to communicate between the different peripherals connected to the bus I/F logic as needed. When non trusted processor cycles are received by processor bus interface logic 104, they are analyzed by the processor bus interface logic 104 and sent to the appropriate bus interface logic. In addition, the processor bus interface logic 104 may respond to the processor 110 from which the trusted cycle or other processor cycles are received with appropriate acknowledgment replies, data cycles, or other cycles.

When I/O bus I/F logic 105 receives the trusted cycle, or the information therein, the I/O bus I/F logic 105 generates a token cycle (i.e., a token read cycle or a special write cycle). In one embodiment of the invention, in order to prevent snooping by bus devices e.g., bus adapters, the token cycle to the token 155 is not to appear on one or more busses other than the I/O bus 162. For example, the token cycle is not to appear on I/O bus 168, I/O bus 169 or I/O 171. In one embodiment of the invention, the token cycle that is generated by the I/O bus interface logic 105 is encoded such that other devices on the I/O bus 162, e.g., the super I/O controller 118 ignore the information contained in the token cycle. In one embodiment of the invention, the I/O bus interface logic 105 receives the trusted cycle and while generating the token cycle sends false data or distorted data on one or more other busses to prevent any information of the token cycle from being echoed and therefore observed on another bus. Only the token cycle sent to token 155, and in particular the I/O bus 162, has the information received from processor bus interface logic 104. So also the information retrieved from token 155 is sent only to processor 110 via processor bus 164. Other busses connected to chipset 120 either do not receive the data, or receive erroneous data. In one embodiment of the invention, I/O bus I/F logic 158 on token 155 receives the data from chipset 120 and writes the data to the appropriate registers in token 155. In other embodiments of the invention, I/O bus I/F logic 158 returns the data requested by token read cycles from chipset 120.

FIG. 5 illustrates a computing device comprising a chipset with a dual ported register according to one embodiment of the invention. In one embodiment of the invention, chipset 120 comprises dual ported registers 111 that couples processor bus I/F logic 104 to I/O bus I/F logic 105. FIG. 6 illustrates a flow diagram for writing to a token using the dual ported registers according to one embodiment of the invention. As illustrated in the embodiment of FIG. 6 at 610 a processor 110 issues a read or write request to chipset 120. At 615, chipset 120 receives the request from processor 110 via processor bus 164. In one embodiment of the invention, after receiving the request from processor 110 chipset 120 decodes the address in the request. In one embodiment of the invention, in addition to decoding the address the chipset 120 decodes the cycle type in the request. At 620, the processor bus I/F logic 104 determines whether the request is a trusted request. In one embodiment of the invention, the processor bus I/F logic 104 determines this by determining whether the decoded address is within the trusted configuration space, and by determining whether a value in a request identity field in the request is a value that indicates the request is a trusted request. If the request is not a trusted request, at 625, the chipset 120 aborts the request. At 630 the processor bus I/F logic 104 determines whether the request targets token 155. If the processor bus I/F logic 104 determines that the request targets token 155 e.g., by determining the offset range is within the specified range, at 635 the chipset 120 latches the data in the request. If the request does not target the token 155, at 625, the chipset 120 aborts the request. At 640, the processor 110 may write to the dual ported registers 111 one or more values for token 155 using for example a standard write transaction. At 645, the processor 110 may then generate a standard I/O write to the token 155, informing the token 155 to fetch the one or more values from the dual ported registers 111 in chipset 120. At 650, the token 155 may become an I/O bus master (using the bus master engine 157) and read the one or more values, written by the processor 110, from dual ported registers 111. In one embodiment of the invention, the token 155 reads the one or more values from the dual ported registers 111 using a code to help ensure that other devices on the I/O bus 162 ignore the token's read cycle. In one embodiment of the invention, the code comprises a reserved binary number that is ignored by other devices on the I/O bus 162. The read values are then stored by I/O bus I/F logic 158 to registers 156 in token 155. At 655 the request is completed.

FIG. 7 illustrates a flow diagram for reading from a token using a dual ported register according to one embodiment of the invention. As illustrated in the embodiment of FIG. 7, at 705, a processor 110 may generate a standard I/O write to token 155, informing the token 155 to write one or more values to dual ported registers 111. At 710, token 155 may become an I/O bus master (using the bus master engine 157) and write one or more values to dual ported registers 111. In one embodiment of the invention, the I/O bus interface logic 158 uses a token cycle that includes a code that ensures that other devices on the I/O bus 162 ignore the write cycle. In one embodiment of the invention, the code comprises a reserved binary number that is ignored by other devices on the I/O bus 162. At 715, the processor 110 issues a read or write request to chipset 120. At 720, chipset 120 receives the request from the processor 110 via processor bus 164. In one embodiment of the invention, after receiving the request from processor 110 chipset 120 may decode the address in the request. In one embodiment of the invention, in addition to decoding the address the chipset 120 decodes the cycle type in the request. At 725, the processor bus I/F logic 104 determines whether the request is a trusted request. In one embodiment of the invention, the processor bus I/F logic 104 determines this by determining whether the decoded address is within the trusted configuration space, and by determining whether a value in a request identity field in the request is a value that indicates the request is a trusted request. If the request is not a trusted request, at 730, the chipset 120 aborts the request. At 735, the processor bus I/F logic 104 determines whether the request targets token 155. If the processor bus I/F logic 104 determines that the request targets token 155 e.g., by determining the offset range is within the specified range, at 740 the chipset 120 provides the latched data to processor 110. If the request does not target the token 155, at 730, the chipset 120 aborts the request. At 740 the chipset 120 provides the latched data in the dual ported registers 111 to the processor 110. At 745 the request is completed.

The interfaces and peripherals connected to chipset 120 may have architecture different from that shown in FIG. 1. In one embodiment of the invention, a memory hub (MCH) comprises the memory bus interface logic 106 that couples memory 130 to the chipset 120. The MCH may include the graphics bus interface logic 109 that connects graphics controller 115 or an accelerated graphics port (AGP) (not shown). Also coupled to the MCH may be an I/O controller hub (ICH). The ICH may include the I/O bus interface logic 105, and a plurality of I/O bus interface logic to connect the ICH to a plurality of I/O devices. In the architecture described above all processor 110 cycles bound for the ICH are received by the MCH and decoded. The MCH forwards configuration space cycles (i.e., trusted cycles) to the ICH for address ranges that do not correspond to registers in the MCH. In one embodiment of the invention, the address ranges that do not correspond to registers in the MCH are address ranges for token 155.

In one embodiment of the invention, the processor 110 trusted cycles for token 155 are normal memory read and write cycles with addresses that match the addresses on the processor bus 164 (i.e., with addresses within a trusted configuration space). In one embodiment of the invention, the ICH ignores memory read and write cycles that address the trusted configuration space but originate from other than the MCH. For example, if a memory read cycle originates from a peripheral component interconnect (PCI) bus with an address in the trusted configuration space, the memory read cycle is ignored by the ICH.

FIG. 3 illustrates a token write cycle on I/O bus according to one embodiment of the invention. In one embodiment of the invention, a token write cycle 300 on I/O bus 162 is used to write information from processor 110 to token 155. In one embodiment of the invention, the token write cycle 300 is a LPC write cycle. The token write cycle comprises a start field 305, cycle type+dir field 310, address (ADDR) field 315, data field 320, turn around (TAR) field 325, synchronous (sync) field 330, and a second turn around (TAR) field 335. However, in order to send the information received from, e.g., the processors 110 or from the processor bus I/F logic 104 to the token 155, the reserved bits in the start field 305 may be used. In one embodiment of the invention, the start field 305 may comprise reserved binary bits (binary numbers) in the range 0100–1110 and may be used to write to token 155. The reserved binary numbers in the start field of the token write cycle 300 are received only by the token 155 on I/O bus 162, and are ignored by other devices e.g., the super I/O controller 118 connected to the I/O bus 162. In one embodiment of the invention, if the other devices on the I/O bus 162 receive the start bits, as soon as the start bits are decoded by the other devices to indicate a reserved binary number, remainder of the token write cycle is ignored. Thus only the token 155 on the I/O bus 162 receives the data from processor 110. Although the embodiment described above uses the reserved bits in the start field of the LPC write cycle, other embodiments may use any other standard that has reserved bits in the start field.

The I/O bus has one control line LFRAME# (not shown) that is used by the chipset 120 to start or stop the transfer of information to and from the token 155. In particular, the LFRAME# signal is asserted during the start field 305 of the token write cycle 300. The chipset 120, and in particular, the I/O bus interface logic 105 may drive data on the token write cycle 300, and then turn the bus around to monitor the token 155 for completion of the cycle. After sending the sync signal 330, the token 155 may then turn the bus around to the chipset 120, ending the cycle.

In one embodiment of the invention the start field 305 indicates the start or stop of a token write cycle 300. All peripherals including token 155 may go to a state that monitors the I/O bus 162 when LFRAME# is active. While LFRAME# is active, the start field 305 may take on many values. Generally, the start field 305 indicates a device number for bus masters, or “start/stop” indication for non-bus master cycles. Normally, peripherals ignore the data being transmitted if a reserved field e.g., 0001 or 0100–1100 is observed, and the data transmitted with the token write cycle 300 is ignored. However, in order to ensure locality wherein the path is guaranteed from e.g., the chipset 120 to the token 155 a reserved binary number is used by the chipset 120 in the start field 305. When token 155 decodes the reserved binary numbers in the start field it responds to the token write cycle 300, and may write the data contained in the token write cycle 300 to one or more of the registers in token 155. Therefore, when the token 155 decodes a start field with e.g., 0101 (a reserved binary number) it responds to the information being transmitted in the token write cycle 300.

FIG. 4 illustrates a token read cycle on I/O bus according to one embodiment of the invention. In one embodiment of the invention, a token read cycle 400 on I/O bus 162 is used to read information from token 155. The token read cycle 400 comprises a start field 405, cycle type+dir field 410, address (ADDR) field 415, turn around (TAR) field 420, synchronous (sync) field 425, a data field 430, and a second turn around (TAR) field 435. However, in order to read information from the token 155, the reserved bits in the start field 405 may be used. In one embodiment of the invention, the start field 405 may comprise reserved binary bits (binary numbers) in the range 0100–1110 or the binary number 0001, and may be used to read token 155. The reserved binary numbers in the start field of the token read cycle 400 are received only by the token 155 on I/O bus 162, and are ignored by other devices e.g., the super I/O controller 118 connected to the I/O bus 162. In one embodiment of the invention, if the other devices on the I/O bus 162 receive the start bits, as soon as the start bits are decoded by the other devices to indicate a reserved binary number, remainder of the token write cycle is ignored. Thus, only the token 155 on the I/O bus 162 receives the read instruction from processor 110.

The I/O bus 162 has one control line LFRAME# (not shown) that is used by the chipset 120 to start or stop the transfer of information to and from the token 155. In particular, the LFRAME# signal is asserted during the start field 505 of the token read cycle 500. The chipset 120, and in particular, the I/O bus interface logic 105 may drive address information on the token read cycle 400, and then turn the bus around to monitor the token 155 for the requested data and the completion of the cycle. After sending the sync signal 425, the token 155 may then send the requested data 430, and turn the bus around to the chipset 120, ending the cycle. Although the embodiment described above uses the reserved bits in the start field of the LPC read cycle, other embodiments may use any other standard that has reserved bits in the start field.

In one embodiment of the invention the start field 405 indicates the start or stop of a token read cycle 400. All peripherals including token 155 may go to a state that monitors the I/O bus 162 when LFRAME# is active. While LFRAME# is active, the start field 405 may take on many values. Generally, the start field 405 indicates a device number for bus masters, or “start/stop” indication for non-bus master cycles. Normally, peripherals ignore the data being transmitted if a reserved field e.g., 0001 or 0100–1100 is observed, and the data transmitted with the token read cycle 400 is ignored. However, in order to ensure locality wherein the path is guaranteed from e.g., the chipset 120 to the token 155 a reserved binary number is used by the chipset 120 in the start field 405. When token 155 decodes the reserved binary numbers in the start field it responds to the token read cycle 400, and obtain data from one or more registers in token 155 and encodes the data in the data field in token read cycle 400. Therefore, when the token 155 decodes a start field with e.g., 0101 (a reserved binary number) it responds to the information requested in the token read cycle 400.

Thus, a method and apparatus have been disclosed to communicate securely with the token, wherein the information sent and received from the token is present only on the processor bus and the I/O bus. While there has been illustrated and described what are presently considered to be example embodiments of the present invention, it will be understood by those skilled in the art that various other modifications may be made, and equivalents may be substituted, without departing from the true scope of the invention. Additionally, many modifications may be made to adapt a particular situation to the teachings of the present invention without departing from the central inventive concept described herein. Therefore, it is intended that the present invention not be limited to the particular embodiments disclosed, but that the invention include all embodiments falling within the scope of the appended claims. 

1. An apparatus comprising: a processor coupled to a first bus to issue a trusted request; a token; and a chipset coupled to the processor by the first bus, said chipset coupled to the token by a second bus, said chipset to decode the trusted request from the processor and to forward the trusted request to the token, said chipset to prevent the trusted request from being echoed on one or more busses other than the second bus.
 2. The apparatus of claim 1 wherein the first bus is a front side bus (FSB) and the second bus is a low pin count (LPC) bus.
 3. The apparatus of claim 2 wherein the chipset sends false data to the one or more busses other than the second bus.
 4. The apparatus of claim 1 wherein the trusted request comprises a request that addresses a trusted configuration space.
 5. The apparatus of claim 1 wherein the trusted request is issued in response to the processor executing microcode or trusted code.
 6. The apparatus of claim 1 wherein the chipset comprises decoder logic to decode an address in the trusted request.
 7. The apparatus of claim 1 further comprising the chipset to encode the trusted request to the token to prevent one or more other devices on the second bus from reading the trusted request.
 8. A method comprising: sending by a processor a trusted request to a chipset; decoding by the chipset the trusted request received from the processor and forwarding the trusted request via a bus to a token using a code, said code selected such that other devices on the bus ignore the trusted request.
 9. The method of claim 8 further comprising suppressing the request on one or more other busses.
 10. The method of claim 8 wherein forwarding the request to the token comprises using reserved bits in the request.
 11. A chipset comprising: a first interface logic to receive from a processor a trusted request via a first bus; a second interface logic coupled to a token via a second bus; a decoding logic coupled to the first interface logic and the second interface logic, said first interface logic to decode the trusted request, said first interface logic to determine that the trusted request is a trusted request from the processor, said first interface logic to further determine that the trusted request targets the token; and the first interface logic to forward the trusted request to the second interface logic if the trusted request targets the token, said second interface logic to prevent the trusted request from appearing on any bus other than the first bus and the second bus.
 12. The chipset of claim 11 wherein the second interface logic sends false data to any bus other than the first bus and the second bus.
 13. The chipset of claim 11 further comprising the second interface logic to encode the trusted request to the token to prevent one or more other devices on the second bus from reading the trusted request.
 14. A token comprising: one or more registers; an input/output (I/O) bus interface logic to couple the token to a chipset via a bus, said token to receive a trusted request from the chipset, said trusted request to comprise reserved bits that are ignored by one or more devices on the bus.
 15. The apparatus of claim 14 wherein the token comprises a bus master engine.
 16. The apparatus of claim 14 wherein the trusted request comprises reserved bits comprising any one of 0001, 0100, 0101, 0110, 0111, 1000, 1001, 1010, 1011, 1100, 1101, and
 1110. 17. An apparatus comprising: a chipset to generate a low pin count (LPC) cycle to a token on a LPC bus, said LPC cycle comprising a start field comprising any one of 0001, 0100, 0101, 0110, 0111, 1000, 1001, 1010, 1011, 1100, 1101, and
 1110. 18. The apparatus of claim 17 wherein the LPC cycle comprises a start field that comprises at least one binary number in the range 0100 to
 1110. 19. The apparatus of claim 17 wherein the chipset is to prevent the LPC cycle from appearing on one or more busses other than the LPC bus.
 20. The apparatus of claim 17 wherein the token on the LPC bus is a trusted plafform module (TPM).
 21. The apparatus of claim 17 wherein the chipset is to cause information contained in the LPC cycle to be invalid if the LPC cycle is present on one or more busses other than the LPC bus.
 22. A machine readable medium comprising instructions which in response to being executed results in a computing device to issue a trusted request from a processor to a chipset, and to forward the trusted request via a bus to a token, said trusted request encoded to form an encoded request such that other devices on the bus ignore the encoded request.
 23. The machine readable medium of claim 22 wherein said instructions to forward the request via a bus to a token, said request encoded such that other devices on the bus ignore the encoded request includes further instructions to generate a low pin count (LPC) cycle to the token, said LPC cycle comprising a start field comprising anyone of 0001, 0100, 0101, 0110, 0111, 1000, 1001, 1010, 1011, 1100, 1101, and
 1110. 24. The machine readable medium of claim 22 wherein the trusted request comprises instructions to address a trusted configuration space in the chipset.
 25. The machine readable medium of claim 22 wherein the chipset is to prevent the encoded request from appearing on one or more busses other than the bus.
 26. A chipset comprising: a dual ported register, said dual ported register to couple a processor to a token, said dual ported register to receive a value for the token from the processor, said processor to write to the token to inform the token to obtain the value from the dual ported register.
 27. The chipset of claim 26 further comprising the processor to write to the dual ported register using trusted microcode.
 28. The chipset of claim 26 further comprising the processor to write to the token using an input/output write cycle.
 29. A method comprising: writing, using a trusted cycle, data to a dual ported register; and generating a standard Input/Output (I/O) write cycle to a token to inform the token to read the data from the dual ported register.
 30. The method of claim 29 further comprising the token to become a bus master to read the data from the dual ported register.
 31. A method comprising: generating a standard Input/Output (I/O) write cycle to a token to inform the token to write data to a dual ported register; and reading, using a trusted cycle, from the dual ported register the data written by the token.
 32. The method of claim 31 further comprising the token to become a bus master to write data to the dual ported register. 